System and method for delivery of voicemails to handheld devices

ABSTRACT

Briefly, a variety of embodiments, including the following, are described: a system embodiment and methods that allow random access to voice messages, in contrast to sequential access in existing system embodiments; a system embodiment and methods that allow for the optional use of voice recognition to enhance usability; and a system embodiment and methods that apply to the area of voicemail.

RELATED APPLICATION

This patent application claims priority to U.S. provisional patentapplication Ser. No. 60/884,414, filed on Jan. 10, 2007, assigned to theassignee of currently claimed subject matter.

FIELD

This disclosure relates to systems and/or methods for delivery ofvoicemails to handheld devices.

BACKGROUND

Existing approaches to voicemail delivery and processing have poorusability, lack functionality, and have poor human-computer interactiondesign. More recent system embodiments have added functionality andaddressed some aspects of the usability drawbacks, but they have notaddressed the fundamental usability limitations and there remains roomfor improvement.

Current approaches assume either voice-only access or a full-fledgede-mail application. Voice-only access is the primary reason for thecurrent limitations of existing voicemail system embodiments. Servicedelivery through voice means that access to stored messages and otherinteractions may not be random and must be sequential, leading to acumbersome method of navigating through a voicemail message list anddifficulty selecting individual messages. In addition, the limitedinterface provides limited access to commands and help functions, withthe end result that many users are not aware of or know how to useadditional functionality, such as replaying messages or accessing callerinformation.

Access through a full-fledged email application or via current onlineinterfaces may require that the recipient of the message have physicalaccess to a computer to access messages. This requirement makes themessages inaccessible if the recipient is mobile and unable to access acomputer.

BRIEF DESCRIPTION OF THE DRAWINGS

Subject matter is particularly pointed out and distinctly claimed in theconcluding portion of the specification. Claimed subject matter,however, both as to organization and method of operation, together withobjects, features, and advantages thereof, may best be understood byreference of the following detailed description when read with theaccompanying drawings in which:

FIG. 1 is a flow diagram of an embodiment;

FIG. 2 is a schematic diagram of an embodiment using telephone number;

FIG. 3 is a schematic diagram of an embodiment using advertising;

FIG. 4 is a schematic diagram showing a detailed view of an inbox for apossible embodiment;

FIG. 5 is a schematic diagram showing a detailed view of an inbox searchprocess for a possible embodiment;

FIG. 6 is a schematic diagram showing crossing linking of audio and textmessages for a possible embodiment;

FIG. 7 is a schematic diagram showing a detailed view of a reply tomessage screen for a possible embodiment;

FIG. 8 is a schematic diagram showing a message server embodiment;

FIG. 9 is a schematic diagram showing a system embodiment;

FIG. 10 is another schematic diagram showing a system embodiment;

FIG. 11 is a schematic diagram showing an output device embodiment;

FIG. 12 is a schematic diagram showing another output device embodiment;

FIG. 13 is a schematic diagram showing an ad message server embodiment;

FIG. 14 is a schematic diagram showing another system embodiment;

FIG. 15 is a schematic diagram showing another output device embodiment;and

FIG. 16 is a schematic diagram showing another ad message serverembodiment.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of the claimed subject matter.However, it will be understood by those skilled in the art that theclaimed subject matter may be practiced without these specific details.In other instances, well-known methods, procedures, components and/orcircuits have not been described in detail so as not to obscure theclaimed subject matter.

Some portions of the detailed description which follow are presented interms of algorithms and/or symbolic representations of operations ondata bits or binary digital signals stored within a computing systemmemory, such as a computer memory. These algorithmic descriptions and/orrepresentations are the techniques used by those of ordinary skill inthe data processing arts to convey the substance of their work to othersskilled in the art. An algorithm is here, and generally, considered tobe a self-consistent sequence of operations and/or similar processingleading to a desired result. The operations and/or processing involvephysical manipulations of physical quantities. Typically, although notnecessarily, these quantities may take the form of electrical and/ormagnetic signals capable of being stored, transferred, combined,compared and/or otherwise manipulated. It has proven convenient, attimes, principally for reasons of common usage, to refer to thesesignals as bits, data, values, elements, symbols, characters, terms,numbers, numerals and/or the like. It should be understood, however,that all of these and similar terms are to be associated with theappropriate physical quantities and are merely convenient labels. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout this specificationdiscussions utilizing terms such as “processing”, “computing”,“calculating”, “determining” and/or the like refer to the actions and/orprocesses of a computing platform, such as a computer or a similarelectronic computing device, that manipulates and/or transforms datarepresented as physical electronic and/or magnetic quantities and/orother physical quantities within the computing platform's memories,registers, and/or other information storage, transmission, and/ordisplay devices.

This application describes a voicemail service that addresses thelimitations of existing system embodiments. One or more embodiments havecombined advancements in telephony, mobile devices, speech recognitionand communications system embodiments in a novel way to offer animproved experience in voicemail system embodiments. In one embodiment,for example, a service delivers voicemails to a user's handset or othersimilar device, complete with transcriptions. The user accesses his orher messages through an email-like inbox, and has the option to sort orsearch for messages. The user may pick any individual message to view.If the individual message is opened, the user may see a systemembodiment transcription of the message. The audio recording of thevoicemail may also be attached and/or linked, either on the handset orthe server, and may also be available for the user to listen to. Theaudio and the text components may be indexed to one another so that theuser may navigate to specific parts of the message via either mechanism.Of course, additional embodiments are also disclosed below.

Please see FIG. 1, High-Level Process Flow of System embodiment, for ahigh-level overview of how a system embodiment works.

In this embodiment, callers to a user of a system embodiment may beforwarded to the user's voicemail inbox if the user is not available. Asystem embodiment may record the caller's message and forward it to atranscription service. The transcription service may transcribe thevoicemail message into text. A delivery service may package thevoicemail audio, text and caller information for delivery. A clientrunning on the user's mobile handset or other similar device may eitherquery a system embodiment for new voicemails, or may be notified that anew voicemail has been received. After notification or awareness of anew message, the client may download the voicemail and make it availablefor the user to view, listen and/or reply from a novel graphical userinterface.

The user may also enjoy various mechanisms to respond to the message.They may have the ability to forward the message to another individual,who may or may not be on a system embodiment. They may have the abilityto respond using a voice message they record on their handset or othersimilar device. A system embodiment may also let the user initiate aconversation, allowing them to record voice messages for delivery tothemselves (as notes), to another individual, or to a specified group.

1.1. Visual Interface to Voicemail System Embodiment

The core of this particular embodiment is a change in the access methodfrom voice to a visual interface. The user may be able to navigate andaccess their messages using point and click mechanisms, similar to theirexisting experiences with web pages and email clients. This allows usersto select messages of interest and access them in a random-access mannerand not have to navigate through any prior messages to gain access. Thetranscription of the message from voice to text allows the user to readthe message instead of hearing it, thereby opening up many more socialsituations and locations where checking of the messages is acceptable.Further, the display of a particular voicemail in a visual interfaceallows for many more and different options to access commands aroundthat voicemail. For example, the user may be able to fast forward themessage as it's playing by pressing a button indicated on the screen,rather than having to navigate away from the message to hear a list ofrelevant commands recited, as happens now under current systemembodiments. The visual display also means that the user may seerelevant content, such as caller number, call time, etc, at once insteadof hearing them sequentially or via special commands.

1.1.1. Voicemail Inbox

The voicemail inbox is the central access point for current voicemailmessages in this embodiment. It presents a list of the messages andmechanisms for the user to navigate among them. The application may berunning either on a mobile handset or other similar device or inside aweb browser, among other devices and/or system embodiments.

1.1.1.1. Listing Voicemails

A system embodiment includes functionality to display current voicemailmessages in a list format. A record displayed includes data includingbut not limited to date, time, caller and a selection of the transcribedmessage text as an aid for navigation and identification of the message.A record may also contain an indicator of status information, such asbut not limited to “New”, “Read” and “Responded”.

Please see FIG. 4: Detailed View of Message Inbox for one example of themessage inbox.

1.1.1.2. Searching Voicemails

A system embodiment includes functionality to search through currentvoicemail messages. The user has the ability to enter search criteriaand receive a list of messages whose transcriptions match the specifiedcriteria. The user may also search fields including but not limited toname, date and message type.

Please see FIG. 5: Message Inbox Search Process for a graphicalrepresentation of the search process.

1.1.1.2.1. Sorting Results by Specified Criteria

Search results may be sorted via predefined criteria. The user mayspecify which criteria they wish to sort by and a system embodiment mayreorder the results based on the criteria and a predefined sort order.

1.1.1.2.1.1. Embodiment: Sort Search Results by Date/Time Received

One embodiment allows the user to sort search results based on the timethat the voicemail is received. The user may select time of message fromthe list of possible criteria and a system embodiment may reorder themessages according to when they were received, earliest to latest.

1.1.2. Individual Voicemail Message View

If an individual voicemail has been selected by the user, a systemembodiment displays the message in its own visual representation. Thisvisual representation includes details on the caller and the message, aswell as the actual content of the message itself. It displays thetranscribed text of the message, and provides access to the audiorecording of the voicemail. It also provides controls where the user maymanage playback of the message as well as respond. The user managesplayback by turning audio playback on or off, fast forwarding orrewinding to certain portions, or otherwise using the navigationmechanisms to navigate around the content of the message. The user mayrespond by using the response mechanisms to perform such actions asforward to another number, forward to email, reply to an individual, andreply to a group or call the sender. The response may also include voiceand/or text from the responder.

1.1.2.1. Navigation

A system embodiment offers a visual method for users to navigate thecontent of the individual message.

1.1.2.1.1. Correlating Audio to Text Transcription

A system embodiment creates an alternate representation of the messagecontent as text. This means that the message is now in at least twoformats: text and the original audio. To improve the user experience,the two formats may cross-index and synchronize to one another.

Please see FIG. 6: Cross-Linking of Audio and Text Representation ofMessage for a graphical representation of how the two formats arelinked.

1.1.2.1.2. Accessing a Particular Point in Audio Through Text Selection

The user may select any word in the text and a system embodiment mayautomatically move to the corresponding point in the audio and beginmessage playback from that point.

1.1.2.1.3. Accessing a Particular Point in Text Through Audio Selection

The user may select any point in the audio playback and a systemembodiment may automatically move to the corresponding point in thetext. To do this the user may use but is not limited to a slider-bar orbuttons on the interface or on the handset or other similar device.

1.1.2.1.4. Replaying a Snippet of Audio by Selecting a Word or Phrase inthe Text

The user may select any word or phrase in the text and a systemembodiment may play just the snippet of audio corresponding to that wordor phrase.

1.1.2.2. Enabling Response by Transforming Telephone Number Text intoLink

A system embodiment recognizes telephone numbers in the transcription ofthe message and automatically creates a link from that number. Selectionof the link by the user initiates a call to the referenced number.Likewise, this concept may be extended to initiate other communicationsother than by telephone number.

1.1.2.3. Enabling Response by Transforming Identifiers in Text into Link

A system embodiment may recognize identifiers, such as names, in thetranscription of the message and automatically create a link from thatidentification. Names or other identifiers may be looked up from auser's handset address book or be included in the message if it isgenerated on the backend. Selection of the link by the user initiates acall to the referenced number.

1.1.2.4. Enabling Easy Addition of Phone Numbers to Phone Book

A system embodiment recognizes telephone numbers in the transcription ofthe message and provides an option for the user to add numbers in themessage to their on-phone phone book. The user may also correct thisnumber in their phone book and that change is reflected in thetranscription.

1.1.3. Ability to Navigate to Individual Voicemail After Notification ofNew Voicemail

A system embodiment includes notifications that a new message has beenleft while the user is not using a provided service. The user may bypassthe inbox and navigate to the new voicemail by taking an action on thenotification display.

1.1.3.1. Embodiment: User May View Voicemail Immediately by Clicking onNotification

One embodiment of this mechanism is providing the user a link along withthe notification of a new voicemail. The user may click the link, whichmay take them to the individual voicemail view for that particularvoicemail. The nature of the link is determined by the phone'sinterface.

1.2. Notification of New Voicemails

One of the more difficult problems to solve in providing this service ishow the handset or other similar device may recognize that a new messagehas been received. Since the message is first received at a centralizedsystem embodiment and the handset or other similar device is by naturemobile and only occasionally connected, it becomes a challenge to keepthe two system embodiments synchronized.

This application describes several mechanisms by which the handset orother similar device may recognize the availability of new voicemails.

1.2.1. Polling Mechanism

One mechanism to check for new voicemails is to periodically query asystem embodiment. Under this mechanism, the handset or other similardevice may initiate a connection to a system embodiment, submitidentifying information and receive as a response the availability andnumber of new messages. Regardless of whether or not new messages havebeen received, the handset or other similar device may wait apredetermined amount of time and perform a query process again. This mayhappen indefinitely.

1.2.2. Event-Triggered Checking

The mobile handset or other similar device may be set to query the mainmessage system embodiment based on certain trigger events. Examples ofsuch events include: missed phone call, entry into coverage area from anarea with no coverage, power-on of the phone, etc.

1.2.2.1. Within a Specified Time Window After a Missed Call

If the user receives notification of a missed call, the handset or othersimilar device may wait a predetermined amount of time and may perform aquery to check for new voicemails. It may be desirable to wait a minimumamount of time to allow the caller to record his message and to allowfor processing time of the recorded message on a system embodiment. Ifthe predetermined amount of time has been met or exceeded, the handsetor other similar device may perform the query to check for newvoicemails.

1.2.2.2. If the Handset or other similar device Enters a Service Area

A user may not receive a call if he or she is out of a coverage servicearea. Furthermore, the query may not be completed without service.However, callers to the user may still leave voicemails at thecentralized system embodiment. As such, if the handset or other similardevice again enters into a service coverage area, there exists thepossibility that a voicemail may be waiting. The handset or othersimilar device may thus initiate a query call upon or relatively soonafter entering a service coverage area.

1.2.2.3. If the Handset or Other Similar Device is Turned on

A user may not receive a call if his or her handset or other similardevice is not turned on. Furthermore, the query may not be completedwithout the handset or other similar device being on. However, callersto the user may still leave voicemails at the centralized systemembodiment. As such, if the handset or other similar device is turnedon, there exists the possibility that a voicemail may be waiting. Thehandset or other similar device may thus initiate a query call upon orrelatively soon after being turned on.

1.2.3. Push Notifications

Another mechanism is for a system embodiment to actively notify thehandset or other similar device that a new message is waiting. As soonas a system embodiment has finished processing a new voicemail message,it may notify the handset or other similar device, which may initiate aquery call to retrieve the new voicemail. Any of several message formatsand delivery channels may be used to deliver this notification from asystem embodiment to the handset or other similar device.

1.2.3.1. Receipt of Specially-Formatted SMS

One option of channel and format is for a system embodiment to send aspecially-formatted SMS to the handset or other similar device. If a newvoicemail has been received and processed on a system embodiment, asystem embodiment may send the SMS to the handset or other similardevice. The SMS is in a special format that the handset or other similardevice recognizes. If an SMS is received, the handset or other similardevice may examine it to see if it is a new voicemail notification. Ifso, the handset or other similar device may initiate a query call to asystem embodiment to retrieve the new voicemail(s).

1.2.3.2. Receipt of Specially-Formatted Push Email

Another option of channel and format is for a system embodiment to senda specially-formatted push email to the handset or other similar device.If a new voicemail has been received and processed on a systemembodiment, a system embodiment may send the email to the handset orother similar device. The email is in a special format that the handsetor other similar device recognizes. If an email is received, the handsetor other similar device may examine it to see if it is a new voicemailnotification. If so, the handset or other similar device may initiate aquery call to a system embodiment to retrieve the new voicemail(s). Notethat this mechanism relies on a “push” email from a system embodiment tothe handset or other similar device, not on the “pull” system embodimentof traditional email which the handset or other similar device may haveseparately.

1.2.4. Combination of any of the Above Methods

The above sections define individual methods of having the handset orother similar device gain knowledge of a new voicemail. In addition tothe individual methods, a combination of the different methods may beused to reduce the number of query calls to a system embodiment whileproviding an improved experience for the user.

1.2.4.1. Conditional Push Notifications

One variation of the Push Notification mechanism above which may beeffectively combined with other methods is a conditional pushnotification. A conditional push notification may be combined withmethods such as event-triggering and polling to achieve prompternotifications and greater coverage than either method alone.

1.2.4.2. Embodiment: Combining Event-Triggered Checking with Polling toIncrease Effectiveness

One possible embodiment of such a combination of methods is combiningevent-triggering with polling. Such a combination may address thescenario where the user receives a voicemail but fails to receive amissed call notification on their handset or other similar device. Underthis scenario, the polling or event-trigger method may work as before,checking from the handset or other similar device to a system embodimentto see if new messages have arrived. A system embodiment may track howlong a new voicemail had been waiting to be delivered. If a new messagehad been waiting longer than a predetermined time, a system embodimentmay proactively send a push notification to the handset or other similardevice. A system embodiment may also monitor responses and stop sendingpush notifications if the new voicemail was not “picked up” within acertain time frame, inferring that the handset or other similar devicewas either out of coverage or turned off, for example.

1.3. Accessing Multiple Message Inboxes on a Single Client

One embodiment of a system embodiment may allow multiple message inboxesto be accessed from a single client. A telephone number registered on asystem embodiment may be linked to an individual inbox. A user mayregister additional telephone numbers to be checked from a singleclient. The client may retrieve the messages from the inbox of anindividual telephone number and may display them in a combined manner onthe user interface.

1.4. Enhancements for Handset or Other Similar Devices with No Data Planor with No Storage Space

The operation of a system embodiment fits well with handset or othersimilar devices with data plans. However, handset or other similardevices with data plans among consumers are currently in the minority,with most consumers not subscribing to a data plan. To reach the largemarket of non-data plan users, a system embodiment is able to providevarious alternatives to enable handset or other similar devices withouta data plan to enjoy aspects of the functionality of a systemembodiment.

1.4.1. Delivery of Voicemails via Push Messaging

One approach employed by a system embodiment to deliver voicemailmessages to handset or other similar devices without data plans is theuse of push messaging. A system embodiment may push the content of thevoicemail, including the audio recording and the text transcription, asa message to the handset or other similar device. The handset or othersimilar device receives the message and the message information istransferred to the visual interface explained above.

One possible embodiment of this concept may use premium MMS to deliverthe message content to the handset or other similar device. The clienton the handset or other similar device may detect the receipt of the MMSand display the delivered message through the user interface.

1.4.2. Accessing a Particular Voicemail Through a Unique TelephoneNumber

A system embodiment may also enable operation on handset or othersimilar devices without a data plan via the use of SMS and the use of apool of centralized, assigned telephone numbers for voicemails. In thismode of operation, a system embodiment may deliver the transcription ofthe response as a text message (SMS) but may not include the audio ofthe response. Instead, a voicemail is linked to a single telephonenumber from a pool of telephone numbers on the backend. The handset orother similar device may dial in to that number. Many voicemails may belinked to any one particular back-end telephone number, but only onevoicemail per user might be linked to any single backend number. Theback-end may determine who is calling that number through the use ofcallerID and may retrieve and play the voicemail linked to thatcombination of caller ID and backend telephone number.

Please see FIG. 2, Use of System embodiment Telephone Numbers and UserTelephone Number to Identify Messages, for a graphical representation ofhow this process works.

1.4.3. Ability to Navigate to Individual Voicemail Through Touch Tones

Another system embodiment enhancement to allow delivery of the serviceto non-data plan phones is the navigation of individual voicemailsthrough touch tones. Under this mode of operation, a system embodimentprovides the visual voicemail inbox, but access to individual messagesis achieved through automatic touch tone input from a system embodiment.The user may view the voicemail inbox on their handset or other similardevice. A system embodiment assigns an integer number to a voicemail. Ifthe user clicks on a particular voicemail, the handset or other similardevice may initiate a phone call to a number specific to the message toaccess the audio of the message. If the call is connected, the user maycontrol audio playback by sending touch tones or predefined audio clipsto the backend.

The backend identifies the specified voicemail through the touch tones.It retrieves the corresponding voicemail and plays back the audiorecording over the cellular connection.

1.4.4. Ability to Navigate to Individual Voicemail Through PreDefinedAudio Clips

Another system embodiment enhancement to allow delivery of the serviceto non-data plan phones is the navigation of individual voicemailsthrough predefined audio clips. Under this mode of operation, a systemembodiment provides the visual voicemail inbox, but access to individualmessages is achieved through predefined audio clips from a systemembodiment. The user may view the voicemail inbox on their handset orother similar device. A system embodiment assigns an integer number to avoicemail. If the user clicks on a particular voicemail, a systemembodiment may send the index of the voicemail selected as predefinedaudio clips to the backend. The backend identifies the specifiedvoicemail through the predefined audio clips. It retrieves thecorresponding voicemail and plays back the audio recording over thecellular connection. Likewise, in some embodiments an audio clip mayinclude tones or DTMF codes.

1.5. Ability to Specify Mixed Access Methods for a User's Messages

A system embodiment allows the user to receive messages through severalmediums. For example, a user may specify their messages be delivered toa telephone number and to an email address. Upon or soon after deliveryof a message, a system embodiment may select the appropriate messageformat and delivery mechanism for that delivery channel. For telephonenumbers, system embodiment messages or SMS mechanisms may be used. Foremail addresses, the message may be sent formatted as an email, with thebody containing the text and the audio file of the message included asan attachment or it may provide a link to a web interface containingthat information as well.

1.6. Authentication

A voicemail comprises a personal communication from one person toanother. As such, care is taken by a system embodiment so that themessage is protected and unauthorized access is not imprudently granted.

1.6.1. Usage of Voice as Password

One method used by a system embodiment to authenticate a user is to usetheir voice as a password. A system embodiment may identify the userbased on their voice and may match that identification to apreviously-stored identification on a system embodiment. If there is amatch, the user is granted access to the stored messages on a systemembodiment. If the voice does not match, the user is denied access andan alert is reported by a system embodiment.

1.6.1.1. Recognition of Spoken Pass Phrase

A system embodiment may also provide another layer of security byallowing the user to speak their pass phrase. If the pass phrase doesnot match the pass phrase stored in a system embodiment, a systemembodiment may refuse authorization.

1.6.2. Counteract Telephone Number Spoofing

A system embodiment relies on the telephone number of the caller toidentify him or her. However, this may expose a system embodiment tosecurity threats since it is possible to falsify CallerID informationand thus present a false telephone number. A system embodiment may takeseveral measures to mitigate this risk.

1.6.2.1. Require Password

A system embodiment may employ a password of any user on a systemembodiment prior to granting access to the user's messages. If thepassword given matches the stored password, access is granted. If thepassword given does not match, the user is denied access and an alert isreported by a system embodiment.

1.6.2.2. Provide a Large-Enough Pool of Telephone Numbers Such That itis Difficult to Guess Correct Combination of Call-in Telephone Numberand User Telephone Number

Section #3.3.2, “Accessing a Particular Voicemail Through a UniqueTelephone Number”, describes a mechanism whereby users with non-dataplan handset or other similar devices may access individual voicemailsthrough a pool of back-end telephone numbers. It may be theoreticallypossible for a malicious attacker to guess the combination of usertelephone number and the call-in telephone number, thereby gainingaccess to the voicemail. To combat this, the pool of telephone numbersmay be increased so as to increase the difficulty an attacker may havein attempting to match telephone numbers.

This type of attack may be fairly efficient if the quantity of call-innumbers is low. As the quantity increases, the probability of this typeof attack succeeding falls. A system embodiment also detects a certainnumber of failed matches and may take action, such as refusing to acceptconnections from the spoofed number for a period of time.

Likewise, an audio clip may, in another embodiment, be sent from theapplication to authenticate the phone. Also, the phone may be programmedto dial a number, and issue a sequence of DTMF codes after the otherside picks up. Thus, one may build an authentication system embodimentalong these lines as well.

1.6.2.3. Usage of Autication Via Audio Clip Sent from Application

A system embodiment may also authenticate the handset or other similardevice from which the call is received through the use of an audio clip.The client on the handset or other similar device may dial a number, andif the server responds to the call, the client may play an audio clip tobe authenticated. The server may either use the audio clip itself ordata contained within the audio clip to identify the handset or othersimilar device and grant access.

1.6.2.4. Usage of Autication Via DTMF Codes Sent from Application

A system embodiment may also authenticate the handset or other similardevice from which the call is received through the use of DTMF codes(e.g., TouchTones). The client on the handset or other similar devicemay dial a number, and if the server responds to the call, the clientmay play DTMF codes to be authenticated. The server may use the DTMFcodes themselves or data contained within the audio clip to identify thehandset or other similar device and grant access.

1.7. Voicereply

The user may have various options to reply to a received voicemail. Oneof these options is the ability to speak a response, which is capturedby a system embodiment, transcribed, and sent to the original caller. Auser may receive a Voicereply in their inbox as they may any regularmessage, except it may be differentiated by a visual marker or by someother method.

Please see FIG. 7: New Message/Reply to message screen for a graphicalrepresentation of the reply process.

1.7.1. Ability to Record and Deliver a Message

A system embodiment provides a mechanism for the user to record a voiceresponse to a message. The message is recorded on the handset or othersimilar device or on a system embodiment. If recorded, the userspecifies one or more recipients for the message. A system embodimentmay transcribe the message into text, and deliver the message to thespecified recipients. The format of the delivered message may depend onwhether or not the recipient is a system embodiment user.

1.7.1.1. Embodiment: Record a Message for Asynchronous Delivery toAnother Recipient

One possible embodiment of such a VoiceReply system embodiment is therecording of a message for asynchronous delivery to another recipient.Under this embodiment, the user initiates a recording through an actionin the application. The recording is made on a system embodiment througha cellular connection. If finished recording, the user enters in atelephone number, or selects a contact from his or her contact addressbook. A system embodiment transcribes the message and prepares it fordelivery. If the recipient is a system embodiment user, the message maybe delivered as a voicemail message. If the recipient is not a systemembodiment user, the message may be delivered as an SMS with the messageaudio available via a call-in number, as described Section #3.3.2Accessing a Particular Voicemail Through a Unique Telephone Number.

1.7.2. Users of System Embodiment

A certain portion of original callers may be system embodiment usersthemselves. For these users, the VoiceReply may appear as any othersystem embodiment-delivered message may, in their inbox.

1.7.2.1. Identify Responses to Earlier Voicemail

In the inbox of the original caller who is a system embodiment user, theVoiceReply may be differentiated to distinguish them from other types ofvoicemail messages. In addition, if the VoiceReply is sent to the systemuser who left the original message, the original message may be linkedto the response or otherwise indicated.

1.7.3. Non-Users of System Embodiment

A far larger portion of original callers may be non-system embodimentusers, at least based on current information. For these users, differenttechniques are employed so that the VoiceReply is accessible on mosthandset or other similar devices, and so that value-added features of asystem embodiment are still accessible.

1.7.3.1. Access a Particular Reply Through a Unique Telephone Number

A system embodiment may not be able to deliver the message in the samemanner to the handset or other similar device of a non-system embodimentuser. For these users a system embodiment may deliver the message asspecified above in Section #3.3.2, “Accessing a Particular VoicemailThrough a Unique Telephone Number”.

1.7.3.2. Provide a One-Time Use Password to Retrieve Reply

In addition to a telephone number used to access the audio of theVoiceReply, a system embodiment may also protect the message using apassword, such as a one-time, disposable password. The one-time passwordis assigned if the message is created and delivered to a non-systemembodiment recipient. The recipient may use this one-time password asauthentication to access the message if calling in. If the passwordmatches that assigned to the message, access is granted. If the passworddoes not match, the request for access is rejected.

1.7.3.2.1. Embodiment: Non-User Receives SMS Notification of Reply withEmbedded Link and One-Time Password

One possible embodiment of such a method is the use of passwords, suchas one-time passwords, to secure a VoiceReply where the user is notifiedvia an SMS. The user may receive the SMS with the name and number of theresponder, as well as the transcribed text of the reply. The SMScontains a link to the stored audio of the reply. Embedded within thatlink is the telephone number assigned to the message. The SMS alsocontains the password generated by a system embodiment for that message.If calling in, a system embodiment may prompt the user to enter thepassword to listen to the audio.

1.7.4. Ability to Specify Multiple Recipients for Delivery of VoiceReply

A system embodiment provides for multiple recipients of a VoiceReply. Arecipient may have the message delivered to them in a format that may beaccessible to them.

1.7.5. Ability to Specify Recipients in Mixed Delivery Channels

A system embodiment allows users to specify different delivery channelsfor the recipients of their voice replies. For example, a user mayspecify that a message be delivered to a telephone number and to anemail address. A system embodiment may select the appropriate messageformat and delivery mechanism for that delivery channel. For telephonenumbers, system embodiment messages or SMS mechanisms may be used. Foremail addresses, the message may be sent formatted as an email, with thebody containing the text and the audio file of the message included asan attachment.

1.7.6. Inclusion of a Link on A Voicereply from a User to a Non-User

On Voicereplies sent to a non-user of a system embodiment, there may bea link, such as on the bottom of the SMS or MMS Voicereply. This linkmay point to the system website or allow the user to download a copy ofthe application software to their mobile phone or other device. In thiscase, the URL starts the application download; special headers sent inthe URL request allow the appropriate application version for thatplatform to be downloaded.

1.8. Voicenote

A user also has the option to initiate a message for delivery tohimself, another individual or group. The user may have the ability tospeak a message, which is captured by a system embodiment, transcribed,and sent to the specified recipients. An alternative implementation mayallow the user to capture the audio stream of a phone conversation ontheir phone or other device. The method of delivery may be through asystem embodiment, as an SMS, as an MMS, or via email. A user mayreceive a Voicenote in their inbox as they may any regular message,except it may be differentiated by a visual marker or via some othermethod.

Please see FIG. 7: New Message/Reply to message screen for a graphicalrepresentation of the Voicenote creation process.

1.8.1. Ability to Record and Deliver a Message

A system embodiment provides a mechanism for the user to record amessage. The message is recorded on the handset or on the back-endsystem embodiment. If recorded, the user specifies one or morerecipients for the message. A system embodiment may transcribe themessage into text, and deliver the message to the specified recipients.The format of the delivered message may depend on whether or not therecipient is a system embodiment user.

1.8.1.1. Embodiment: Record a Message for Asynchronous Delivery toAnother Recipient

One possible embodiment of such a VoiceNote embodiment is the recordingof a message for asynchronous delivery to another recipient. Under thisembodiment, the user initiates a recording through an action in theapplication. The recording is made on a system embodiment through acellular connection. If finished recording, the user enters in atelephone number, or selects a contact from his or her contact addressbook. A system embodiment transcribes the message and prepares it fordelivery. If the recipient is a system embodiment user, the message maybe delivered as a voicemail message. In the inbox, the message may bemarked as a VoiceNote using colors, text or some other visual symbol orother approach to differentiate it from other types of messages. If therecipient is not a system embodiment user, the message may be deliveredas an SMS with the message audio available via a call-in number, asdescribed above.

1.8.1.2. Embodiment: Record a Message for Asynchronous Delivery toYourself

Another possible embodiment of such a VoiceNote embodiment is therecording of a message for asynchronous delivery to the user themselves.Under this embodiment, the user initiates a recording through an actionin the application. The recording is created on a system embodimentthrough a cellular connection. If finished recording, the user indicatesthat the message is for him or her. A system embodiment transcribes themessage and prepares it for delivery. The message is delivered as avoicemail message. In the inbox, the message may be marked as aVoiceNote using colors, text or some other visual symbol or otherapproach to differentiate it from other types of messages.

1.8.2. Users of System embodiment May Receive Voicenotes

Since the person receiving the note is a system embodiment user, theVoiceNote may appear as any other system embodiment-delivered messagemay, in their inbox.

1.8.3. Users of System Embodiment May Send Voicenotes to their Own Inbox

By specifying themselves as the recipient of a Voicenote users may sendthemselves Voicenotes.

1.8.3.1. Embodiment: Capturing a 411 Phone Conversation

The user dials 411. They ask for the phone number for a take-outrestaurant. They navigate to the system and start recording theconversation as a new Voicenote. If the conversation is done the note issent down to the server, transcribed and placed in the user's voicemailbox. The user has the record of the phone number and may use theclick-to-call feature, mentioned previously, to call the restaurant.

1.8.4. Non-Users of System Embodiment

A far larger portion of recipients, based on current information, may beindividuals who are not currently system embodiment users, and who maythus not have a client installed on their handsets or other device. Forthese users, different techniques are employed so that the VoiceNote isaccessible on most devices, and so that value-added features of a systemembodiment are still accessible.

1.8.4.1. Access a Particular VoiceNote Through a Unique Telephone Number

A system embodiment may not be able to deliver the message in the samemanner to the handset or other similar device of a non-system embodimentuser. For these users a system embodiment may deliver the message asspecified above in Section #3.3.2, “Accessing a Particular VoicemailThrough a Unique Telephone Number”.

1.8.4.2. Require a Password to Retrieve Reply

In addition to the telephone number used to access the audio of theVoiceNote, a system embodiment may also protect the message using apassword. The password may be a one-time password. The password may beassigned if the message is created and delivered to a non-systemembodiment recipient.

The recipient may use this password as authentication to access themessage upon or soon after calling in. If the password matches thatassigned to the message, access is granted. If the password does notmatch, the request for access is rejected.

1.8.4.2.1. Embodiment: Non-User Receives SMS Notification of Reply withEmbedded Link and One-Time Password

One possible embodiment of such a method is the use of passwords tosecure a VoiceNote where the user is notified via an SMS. The user mayreceive the SMS with the name and number of the responder, as well asthe transcribed text of the reply. The SMS contains a link to the storedaudio of the reply. Embedded within that link is the telephone numberassigned to the message. The SMS also contains thee password generatedby a system embodiment for that message. If calling in, a systemembodiment may prompt the user to enter the password to listen to theaudio.

1.8.4.3. Inclusion of a Link on a Voicenote from a User to a Non-User

If Voicenotes are sent to a non-user of a system embodiment, there maybe a link, such as on the bottom of the Voicenote. This link may pointto the system website or allow the user to download a copy of theapplication software to their mobile phone or other device. In the casethat the URL starts the application download, special headers sent inthe URL request allow the appropriate application version for thatplatform to be downloaded.

1.8.5. Ability to Specify Multiple Recipients for Delivery of VoiceNote

A system embodiment provides for multiple recipients of a VoiceNote. Arecipient may have the message delivered to them in a format that may beaccessible to them.

1.8.6. Ability to Specify Recipients in Mixed Delivery Channels

A system embodiment provides for recipients in different deliverychannels to be specified. For example, a user may specify that a messagebe delivered to a telephone number and to an email address. A systemembodiment may select the appropriate message format and deliverymechanism for that delivery channel. For telephone numbers, systemembodiment messages or SMS mechanisms may be used. For email addresses,the message may be sent formatted as an email, with the body containingthe text and the audio file of the message included as an attachment.

1.8.7. Attachments

Converting voicemails to other message formats enables the service toattach other items to the message. Any number of additional items may beattached, by a system embodiment or by the user.

1.8.8. Ability to Include Attachments in VoiceNote or VoiceReply

One logical place to include attachments is in the VoiceNote orVoiceReply message. Attachments may be included with the originalcontent. Of course, this is simply an example embodiment.

1.8.8.1. Embodiment: Include Document as Attachment to VoiceReply

One possible embodiment of such a system embodiment may allow the userto attach a document already present on the handset or other device asan attachment to a VoiceReply. A scenario may be envisioned where theuser receives a voicemail from another individual asking them for adocument. The recipient may initiate a VoiceReply, but add the requesteddocument as an attachment to the response.

1.9. Viral Marketing

Voicemails lend themselves well to marketing. A system embodiment mayinclude several features that facilitate the spread of the handset orother device client through person to person methods.

1.9.1. Ability to Invite a Non-User

A system embodiment includes the ability to invite a non-user of asystem embodiment onto a system embodiment. A current user may specifythe contact information for a non-user, and a system embodiment may sendthe invited user a notification that allows them to enroll in a systemembodiment.

1.9.1.1. Embodiment: Invite a Friend

One possible embodiment of this functionality is a feature that allows acurrent user to invite another, such as a “friend,” onto a systemembodiment. The current user may select the “Invite a Friend” or otherlink on the application. The application displays a prewritten,preformatted text message. This message may be sent to the invitedfriend, for example. The original user is allowed to edit and customizethe message. If finished, the original user may press “Invite”. At thatpoint, a system embodiment may send the invited friend a notificationtext message with a link and instructions on how to enroll. The inviteemay download the application and enroll in the service entirely orpartially through the mobile handset or other device.

1.9.2. Ability to Sign Up Entirely on a Handset or Other Similar Device

To facilitate sign ups of potential new users, a system embodiment mayallow new users to enroll via their handsets or similar devices withoutthe necessity of a more complex platform, such as a computer, forexample. Data collection, interaction and notifications may be done viasuch devices and the new user may be able to complete the registrationprocess without moving to a more complex device.

1.9.3. Link Included on Every VoiceReply

A system embodiment may include a link to sign up for the service onvoice messages sent in response to a previous voice message received bya user of the service. The outbound voice message may include a link tosign up somewhere within the message reply. The recipient of the replymay have the opportunity to click on the link, at which point they maycommence the enrollment process.

1.9.4. Link Included on Every VoiceNote

A system embodiment may include a link to sign up for the service onvoice messages sent by a user of the service. The outbound voice messagemay include a link to sign up somewhere within the message content. Therecipient of the reply may have the opportunity to click on the link, atwhich point they may commence the enrollment process.

1.10. Delivery of Voicemails via Alternate Channels

Specifically, a system embodiment may deliver the messages to channelsother than a handset or similar handheld devices. People may prefer toreceive messages in their current working environment. A systemembodiment's centralized receipt and storage of messages allows themessage to be sent out over various delivery channels.

1.10.1. Plugin for Desktop Email Clients

One delivery channel for voicemail messages are desktop email clients. Asystem embodiment may include a plugin to desktop email clients whichmay perform similar functions as the handset or other handheld devicewith regards to checking, listing and displaying messages.

1.10.1.1. Embodiment: Plugin for Microsoft Outlook

One possible embodiment of such a system embodiment is a plugin forMicrosoft Outlook. This plugin may integrate received voicemail messagesseamlessly with standard received email. It may perform the functions ofchecking, listing, and displaying messages.

1.10.2. Plugin for Mobile Email Clients

Another delivery channel for voicemail messages are in mobile emailclients. A system embodiment may include a plugin to mobile emailclients which may perform similar functions as the standard applicationwith respect to checking, listing and displaying message

1.10.3. Delivery Through Email System Embodiments

In addition to the plugin mechanism described above, voicemail messagesmay also be delivered as embedded objects or links within standardemails. The user may receive the email and may activate the embeddedobject or click on the link to open the voicemail. The message may bereplayed within the email message itself, or within a new webpage openedfrom the email message.

1.10.3.1. Embodiment: Delivery of Voicemails to Online Email Services

One possible embodiment of such a system embodiment is embedding a linkto the voicemail message stored on a system embodiment in an email sentto the user. The user clicks on the link, which opens a new webpage withthe voicemail message embedded within it. The user clicks on specifiedcontrols to play, rewind or fast-forward the message. The user also mayview the message transcription on this page and interact with the audioand the transcription as discussed in section 3.1.2.1 “Navigation.”

1.10.4. Delivery Through Instant Messaging System embodiments

Another delivery channel for voicemail messages are instant messagingsystem embodiments. A system embodiment may include a plugin to IMclients which may perform similar functions as a handset or similarhandheld device with regards to checking, listing and displayingmessages. A system embodiment may also deliver the voicemail messagethrough the IM channel, treating it as an Instant Message itself, forexample. A system embodiment may also use the built-in capabilities ofan IM client to deliver the message, such as using any integration withaudio speakers to play the audio portion of the message.

1.10.4.1. Embodiment: Plugin for IM Clients

One possible embodiment of such a system embodiment is a plugin for IMclients such as Yahoo Messenger. This plugin may integrate receivedvoicemail messages seamlessly with standard received IMs. It may performthe functions of checking, listing, and displaying messages.

2. Speech Recognition

A system embodiment makes use of speech recognition, especially in thearea of transcribing the content of the voicemail to text. A systemembodiment contains various novel applications of speech recognition, aswell as methods to enhance the accuracy of the speech recognition.

2.1. Provision of Speech Recognition as a Network-Centric Service

A system embodiment represents a novel delivery of speech recognitionservices as a network-centric service. The speech recognitionfunctionality resides on a network and makes its functionalityaccessible through interfaces into and out of a system embodiment. Asystem embodiment receives audio input on its input interface. Itdetermines the format of audio input and identifies the correct handlerfor the determined format. A system embodiment also determines thespeech to text engine to use to convert the speech to text, asdetermined via a system embodiment configuration, and invokes thatengine to convert the audio into text. A system embodiment returns theconverted text to the calling system embodiment. The speech recognitionnetwork service may operate without training, but if training or samplesare available, it may make use of them to enhance accuracy.

2.2. Use of Speech Profiles for Individuals Using or Calling Into SystemEmbodiment

As a method to improve the accuracy of speech recognition, a systemembodiment maintains a speech profile for individuals whose speech isbeing transcribed. Recordings made by individuals on a system embodimentmay be stored and added to their profile to build a set of speechsamples for that individual. This set of speech samples may be laterused to improve the accuracy and/or efficiency of the speech recognitionengine.

2.2.1. Use of Speech Profiles for Individuals Who are not Current Usersof a System Embodiment

A system embodiment may maintain speech profiles not only for currentusers of a system embodiment, but also for individuals external to asystem embodiment who call those users. A system embodiment may usethese profiles of external individuals to improve the accuracy of thespeech recognition in a similar manner that it may use the profiles ofthe current system embodiment users.

2.3. Identification of Individuals through Speaker Identification

A system embodiment may be able to determine the identity of the callerthrough the characteristics of their voice. This identification may beused in improving speech recognition, such as automatically retrievingthe voice profile for that user.

2.4. Identification of Individuals Through Knowledge of which Cell Phoneis Being Used

A system embodiment may be set up so as to assume that the speaker on acell phone or similar device is the only one that uses that that device.By this setting, messages arriving from this phone are associated withthe cell phone owner's speech profile.

2.5. Training of System embodiment to Improve Performance

A system embodiment includes features that enable the use of training toimprove the accuracy of the speech recognition. The training may beconducted by any of the individuals involved, or by external parties.

2.5.1. Training of System embodiment by Sender

A system embodiment may allow training by the sender. The sender mayspecify the correct transcription to captured audio from himself orherself.

2.5.1.1. Embodiment: System Embodiment to Allow Sender to Train SystemEmbodiment by Correcting Errors

One possible embodiment of such a system embodiment is a systemembodiment that enables the sender to train a system embodiment onrecorded audio. For example, the sender may speak their message, waitfor a system embodiment to transcribe it, and be presented with thetranscription results. The sender may correct any mis-transcribed words.A system embodiment may record the corrections and create an updatedmodel of the sender's speech for use in later transcriptions from thesame user.

2.5.2. Training of System Embodiment by Recipient

A system embodiment may allow training by the recipient. The recipientmay specify the correct transcription to captured audio from aparticular sender.

2.5.2.1. Embodiment: System Embodiment to Allow Recipient to TrainSystem Embodiment by Correcting Errors from Specific Senders

One possible embodiment of such a system embodiment is a systemembodiment that enables the recipient to train a system embodiment onrecorded audio from a particular sender. For example, the sender mayspeak their message and have it delivered to the user, as with thenormal operation of a system embodiment. The user may receive themessage, but may have the option to correct any mis-transcribed words. Asystem embodiment may record the corrections and create an updated modelof the sender's speech for use in later transcriptions from the samesender.

2.5.3. Training of System Embodiment via Manual Verification

A system embodiment may allow training via manual correction.Transcribed messages from a particular caller may be routed for manualtranscription or for manual correction. The changes may be recorded by asystem embodiment and used to enhance the accuracy of speech recognitionon messages from that particular sender. A system embodiment trainingusing these manual transcriptions may continue until adding additionaltranscriptions into a system embodiment may negligibly or otherwise notsignificantly improve the transcription quality for the speaker, such asthrough an improvement measure.

2.5.3.1. Embodiment: Use of Transcribers to Train System Embodiment byCorrecting Errors

One possible embodiment of such a system embodiment is a systemembodiment that enables the routing of messages to people who maytranscribe it or make corrections in the machine transcription. Thesender may speak their message and have it delivered to the user, aswith the normal operation of a system embodiment. The user may receivethe message. However, the message and transcription may also be sent toa call center where the message transcription may be corrected. A systemembodiment may record the corrections and may add them to a model of thesender's voice. A system embodiment may use this model to enhance theaccuracy of later messages from the same sender.

2.5.3.2. Embodiment: Use of Transcribers to Train System Embodiment byDirect Transcription

Another possible embodiment of such a system embodiment is a systemembodiment that enables the routing of messages to people who maytranscribe them manually. The sender may speak their message and have itdelivered to the user, as with the normal operation of a systemembodiment. The user may receive the message. However, the message mayalso be sent to a call center where employees may transcribe the messagemanually or where it may be done with a combination of automatic andmanual approaches. This may be done by having the employees repeat themessage into another speech recognition system embodiment highly trainedon their voice and through a high quality microphone. The accuratetranscriptions and the original audio may be added to the sender's modelto enhance the accuracy of later messages from that sender.

2.5.4. Training of System Embodiment Via Web-Based System EmbodimentLinked to Recording for Manual Correction

A system embodiment may also offer a web-based interface linked to ahandset or other similar device for manual correction by a user. Thevoice is recorded and sent to the backend. The recording may be done onthe handset or other similar device and sent to the backend, or therecording may be done on the backend via a cellular connection. Thebackend performs speech recognition on the recording and displays thetranscribed message on the web-based interface, such as, simply as oneexample, words where the transcriber indicates more than one possibilitythrough special marking. If the user selects those words, such as via aninput device, as an example, a mouse click, a list of alternatetranscriptions are displayed. The user may correct the transcription bypicking an alternate transcription from the list. The user may alsocorrect the transcription by manually editing a single word or phrase.

2.5.5. Training of System Embodiment via Web-Based Interface, Script andCellular Connection

A system embodiment may allow training via a web-based interface and acellular connection. Traditional systems enable training only via acomputer application and a computer microphone. A system embodiment heremay provide a mechanism where a web-based interface is used to display aknown script to the user. The user's spoken speech is captured via acellular connection on a handset or similar device, and transcribed withthe original script as a known comparison sample. This mechanism doesnot require the use of any computer microphones or applications, otherthan a browser, running on the computer.

2.5.5.1. Embodiment: Web-Based Interface and Cellular Connection

One possible embodiment of such a system embodiment is a systemembodiment that enables training via a web interface. The web interfacedisplays a known script. The user calls a specified number on hishandset or other similar device and starts speaking the known script.The user indicates the completion of a section of text through the useof codes, such as dialing a ‘9’ to indicate the end of a paragraph. Thisallows for an improved training experience using dynamic text. The audiois recorded on the back-end system embodiment. The audio is transcribed,using the known script as a comparison sample for the transcriber to usein determining the correct transcription.

2.6. Use of Different Sound Capture Quality

Since a system embodiment is able to recognize who is recording themessage, several improvements may be made to sound quality and speechtranscription. For example, sound recorded on a handset or similardevice may be recorded at a higher quality than sound that is recordedthrough a cellular connection. The higher quality of the recordingresults in a higher quality transcription.

2.6.1. Embodiment: Record a Message for Asynchronous Delivery to AnotherRecipient

One possible embodiment of using different sound capture quality is therecording of a message for asynchronous delivery to another recipient.Under this embodiment, the user initiates a recording through a command.The recording is made on the handset or similar device and is recordedat a higher quality than may otherwise be available if the recordingwere made through a cellular connection. If finished recording, the userenters in a telephone number, or selects a contact from his or hercontact address book. A system embodiment transcribes the message andprepares it for delivery. If the recipient is a system embodiment user,the message may be delivered as a voicemail message. If the recipient isnot a system embodiment user, the message may be delivered as an SMSwith the message audio available via a call-in number, as describedabove.

2.6.2. Embodiment: Record a Message for Asynchronous Delivery toYourself

Another possible embodiment of using different sound capture quality isthe recording of a message for asynchronous delivery to the userthemselves. Under this embodiment, the user initiates a recordingthrough an action in the application. The recording is made on thehandset or other similar device and is recorded at a higher quality thanmay otherwise be available. If finished recording, the user indicatesthat the message is for him or her. A system embodiment transcribes themessage and prepares it for delivery. The message is delivered as avoicemail message.

2.6.3. Embodiment: Switch from Leaving a Voicemail to Recording on theHandset or Other Similar Device for System Embodiment Users

Another possible embodiment of using different sound capture qualityarises if a system embodiment user calls another system embodiment userand is directed to a voicemail system embodiment. Under that case, asystem embodiment may detect that the sender is leaving a message andthat both the sender and the recipient of a voicemail are systemembodiment users. It may switch the sender from leaving a messagethrough a cellular call to having the message be recorded on the handsetor other similar device client at a higher sound capture quality level.The recorded message becomes a VoiceNote and gets delivered through theVoiceNote mechanism.

2.6.4. Embodiment: Switch from Leaving a Voicemail to Recording on theHandset or Other Similar Device for all Users

Another possible embodiment of using different sound capture qualityarises if a system embodiment user calls any telephone number and isdirected to a voicemail system embodiment. Under that case, a systemembodiment may detect that the caller is leaving a message and switchthe sender from leaving a message through a cellular call to having themessage be recorded on the handset client or similar device at a highersound capture quality level. The recorded message becomes a VoiceNoteand gets delivered through the VoiceNote mechanism.

2.7. Option to Improve Transcription by Requesting Manual Transcription

A system embodiment may also offer the use of all-manual transcriptionor a mix of automatic and manual approaches. Users may be able tospecify that they wish to receive only manually-transcribed messages ora mix. Senders of messages to these users may be able to leave theirvoicemail messages as before. However, instead of transcribing themessage via the automated system embodiment, the audio is sent to a callcenter where the message is transcribed manually or via a mix ofapproaches. If the transcription is complete, the message is deliveredto the user through a similar approach as other messages for otherusers.

3. Advertising

A system embodiment offers advertising to handsets or other similardevices. This advertising is in the context of the delivered voicemail.The advertising may be linked to the delivered voicemail message and/ormay be targeted by factors such as user factors or environmentalfactors. The advertisement may also be untargeted and not selected basedon any user or environmental factors. Thus, this embodiment includes thecombination of advertising and voicemail on a mobile handset or othersimilar device. Furthermore, this embodiment includes targetingadvertising in the context of voicemail on a mobile handset or othersimilar device.

3.1. Provide Voicemail Service Free of Cost to Users in Exchange forAdvertisement on the Service

A system embodiment may offer the service to users who have agreed toreceive advertisements with various attractive financial arrangements,including without charge, for example. These advertisements may be indifferent formats, in different areas, and displayed in differentmanners.

3.1.1. Banner-Type Ads on Inbox

The handset or other similar device may display banner-typeadvertisements on the Inbox screen. The advertisement may be displayedin different sections of the screen. The advertising space may also berotated among at least one placement on the screen.

3.1.2. Banner-Type Ads on Individual Voicemail View

The handset or other similar device may display banner-typeadvertisements on the individual voicemail view screen. Theadvertisement may be displayed in different sections of the screen. Theadvertising space may also be rotated among at least one placement onthe screen.

3.1.3. Application “Daily Pass”

The handset or other similar device may display a single advertisementon the first voicemail checked by a user on any given calendar day.Seeing the advertisement allows the user to access the rest of his orher voicemails for that calendar day without having to view additionaladvertisements.

3.1.4. “Interceptor” Ads on Individual Voicemail View

The handset or other similar device may display advertisements beforeshowing the user an individual voicemail view. The advertisement may bedisplayed for a short period of time, and may disappear and the selectedvoicemail message view may be displayed.

Please see FIG. 3, Advertising Inserted Before Viewing An IndividualVoice Message, for a graphical representation of one possibleimplementation of such an advertising method.

3.1.4.1. Ability to View Shown Ad by Clicking Link on IndividualVoicemail View

A system embodiment may provide a method for the user to retrieve anadvertisement shown prior to viewing the voicemail message view. Theuser may be able to click on a link to display the advertisement.

3.1.2.2 Ability to View Previous Ads Via Advertising Inbox

A system embodiment may provide an approach for the user to access anadvertisement previously displayed. The user may be able to click on alink to view a list of previously-displayed advertisements, for example.The user may select one of the advertisements from the list. Ifselected, a system embodiment may display the advertisement.

3.2. Advertisements on Responses from Recipients to Senders (VoiceReply)

A system embodiment may include advertisements with responses fromrecipients of voicemail messages to the sender of the message.

3.2.1. Embodiment: Include Advertisements on VoiceReply Responses

One possible embodiment of such a system embodiment may include anadvertisement on messages sent as a response to a sender of voicemail.The sender may receive both the response and the associatedadvertisement.

3.3. Advertisements on Messages Initiated by Users (VoiceNotes)

A system embodiment may include advertisements on messages initiated byusers to specified recipients.

3.3.1. Embodiment: Include Advertisements on VoiceNotes

One possible embodiment of such a system embodiment may include anadvertisement on messages sent as a VoiceNote to one or more recipients.The recipient may receive both the sent message and the associatedadvertisement.

3.4. Format of Advertising

The advertising shown may be in any number of different formats. Formatsmay be selected based on the handset or other similar device'scapabilities. The same handset or other similar device may also displaydifferent formats.

3.4.1. Video

A system embodiment may support video as an advertisement format.Advertisements may be received and displayed in any of several possiblevideo formats.

3.4.2. Rich Media

A system embodiment may support rich media as an advertisement format.Advertisements may be received and displayed in any of several possibleformats which are interactive and/or allow motion or other actions.

3.4.2.1. Embodiment: Flash-Style Advertisements

One possible embodiment of a system embodiment may support rich mediathrough the support of Flash. Advertisements may be received as Flashfiles, and displayed through the invocation of a Flash player residenton the handset or other similar device, or downloaded and installed aspart of download and installation.

3.4.3. Coupons

A system embodiment may support coupons as an advertisement format.Advertisements may be received and displayed in any of several possibleformats which are redeemable at the advertising merchant location orthrough other methods of purchase. These types of advertisements mayinclude a redemption code or other method to identify the offer.

3.4.4. Images

A system embodiment may support images as an advertisement format.Advertisements may be received and displayed in any of several possibleimage formats which are supported by the user's handset or other similardevice.

3.4.5. Text

A system embodiment may support text as an advertisement format.Advertisements may be received and displayed in any of several possibletext formats.

3.5. User Response Mechanisms to Advertisements

Users may have various mechanisms available to respond to a displayedadvertisement.

3.5.1. Click-To-Call

A system embodiment may provide the ability to click on a telephonenumber and/or link embedded within an advertisement and may have theuser's handset or similar device call that number.

3.6. Untargeted Advertising

A system embodiment may have the ability to display advertisements thatare not selected on the basis of any user or environmental factors.

3.7. Targeted Advertising

A system embodiment may have the ability to select advertisements basedon a single factor or combination of factors. These are factors may bederived from the message, message transcription, user, environment orany other source.

3.7.1. Message-Specific Factors

One set of factors that may be used for selecting advertisements arefactors that are specific to the received message.

3.7.1.1. Content of Voicemail

A system embodiment may use the content and the words inside of avoicemail message as factors in the selection of an advertisement todisplay. The content itself or factors derived from the content may beused to select advertisements.

3.7.1.1.1. Select Advertisements Based on Keywords in VoicemailTranscription

One possible embodiment of this system embodiment may extract keywordsfrom the transcription of the message and use those keywords to selectadvertisements. Advertisements may have a set of related keywordsassociated with them. A system embodiment may attempt to match keywordsassociated with the message and keywords associated with theadvertisement to determine a match. The advertisement with a match basedon a measurement of the quality of the match, for example, may beselected and sent to the handset or other device along with thevoicemail message. If the user selected that particular voicemail fordisplay, the handset or other similar device may show them the selectedadvertisement before displaying the content of the message.

3.7.1.1.1.1. Embodiment: Advertisements Based on Keywords in VoicemailTranscription

Here is an example of a possible system embodiment implementation:Someone leaves a user a message that mentions they want to have a PapayaSmoothie. The message transcription contains the keywords “Papaya” and“Smoothie.” These keywords match advertisements related to smoothies.One of these ads, in this case a smoothie shop ad, gets shown to theuser.

3.7.1.1.2. Select Advertisements Based on Concepts Extracted fromVoicemail Transcription

One possible embodiment of this system embodiment may extract theconcepts from the transcription of the message and use those concepts toselect advertisements. A concept is above the level of an individualword or phrase and represents an idea, place, or person that may berepresented by any number of individual words or phrases. Advertisementsmay have a set of related concepts associated with them. A systemembodiment may attempt to match the concepts associated with the messageand the concepts associated with the advertisement to determine a match.The advertisement with a match, again based on a measurement of thequality of the match, for example, may be selected and sent to thehandset or other device along with the voicemail message. If the userselected that particular voicemail for display, the device may show themthe selected advertisement before displaying the content of the message.

3.7.1.1.2.1. Embodiment: Select Advertisements Based on ConceptsExtracted from Voicemail Transcription

Here is an example of a possible system embodiment implementation:Someone leaves a user a message that mentions the keywords “trail,”“boots” and “tent.” These keywords are mapped to the concept of outdoorsand camping. These concepts match advertisements related to stores thatsell camping supplies. One of these ads, in this case Ed's CampingSupplies, gets shown to the user.

3.7.1.1.3. Select Advertisements Based on Profile of Message

One possible embodiment of this system embodiment may determine whichknown profile a message belonged to and may use that profile to selectadvertisements. A profile may comprise an archetype or schema for amessage, and messages with similar profiles may be inferred to refer tosimilar communications. For example, it may be determined that a certaincombination of words around 6 pm usually indicates dinner plans. Thatcombination of words and time may thus become a profile, which maycomprise a signature for a type of message. Advertisements may have aset of related message profiles associated with them. A systemembodiment may attempt to match the profile associated with the messageand the profile associated with the advertisement to determine a match.The advertisement with a match, again, based on a quality measure, forexample, may be selected and sent to the handset or other device alongwith the voicemail message. IF the user selected that particularvoicemail for display, the handset or other similar device may show themthe selected advertisement before displaying the content of the message.

3.7.1.1.3.1. Embodiment: Select Advertisements Based on Profile ofMessage

Here is an example of a possible system embodiment implementation:Someone leaves a user a short message at 6 pm on Valentine's day thatmentions the keywords “movie” and “dinner.” This combination ofkeywords, date and time are mapped to the concept of “romance.” Thisconcept matches advertisements for florists. One of these ads forflorists, gets shown to the user.

3.7.1.2. Sender of Message

A system embodiment may use the sender of a voicemail message as afactor in the selection of an advertisement to display. The sender orfactors derived from the sender and/or his or her preferences and/or hisor her relationship with the recipient(s) may be used to selectadvertisements.

3.7.1.2.1. Embodiment: Infer Relationship With Sender Based on CallingProfile

One possible embodiment of this system embodiment may infer therelationship between the sender and the recipient based on the callingprofile between the sender and the recipient. For example, a frequentlycalled person by a user may be inferred to be close to that person, suchas a significant other. Advertisements may have a set of relatedrelationships associated with them. A system embodiment may attempt tomatch the relationship associated with the sender and the relationshipassociated with the advertisement to determine a match. Theadvertisement with a quality match may be selected and sent to thehandset or other device along with the voicemail message. If the userselected that particular voicemail for display, the handset or othersimilar device may show them the selected advertisement beforedisplaying the content of the message.

This mechanism may be combined with other known data, for example,holidays such as Valentine's Day. One example of targeting may displayan ad for a romantic dinner for two if that special person called onthat day, while displaying normally-selected ads for other callers.

3.7.1.2.2. Embodiment: Infer Relationship With Sender Based onRecipient's Address Book

One possible embodiment of this system embodiment may infer therelationship between the sender and the recipient based on therecipient's handset or other address book. For example, the sender'sposition in the user's speed dial list of numbers may be used to inferthe level of the relationship between recipient and sender.Advertisements may have a set of related relationship levels associatedwith them. A system embodiment may attempt to match the relationshiplevel associated with the sender and the relationship level associatedwith the advertisement to determine a match. The advertisement with aquality match may be selected and sent to the handset or other similardevice along with the voicemail message. If the user selected thatparticular voicemail for display, the handset or other similar devicemay show them the selected advertisement before displaying the contentof the message, for example.

3.7.1.2.3. Embodiment: Target Advertising Based on Sender's Preferences

One possible embodiment of this system embodiment may infer thepreferences of the recipient based on the preferences of the sender, ifthe sender's preferences were already available to a system embodiment.For example, if a system embodiment recognizes that a sender had apreference for a certain type of meal, based on the senders advertisingprofile, a system embodiment may infer that recipients of thatparticular sender's messages may also have a similar preference for thatcertain type of meal. Advertisements may be targeted on that preference.A system embodiment may attempt to match the implied preferenceassociated with the sender and the preference associated with anadvertisement to determine a match. The advertisement with a qualitymatch may be selected and sent to the handset or other similar devicealong with the voicemail message. If the user selected that particularvoicemail for display, the handset or other similar device may show themthe selected advertisement before displaying the content of the message,for example.

3.7.1.3. Time of Day

A system embodiment may use the current time of day that the voicemailwas sent as a factor in the selection of an advertisement to display.The time of day itself or factors derived from the time of day may beused to select advertisements.

3.7.1.3.1. Embodiment: Infer Intent of Voicemail Through Time of DayReceived

One possible embodiment of this system embodiment may infer the intentof the voicemail on the basis of the time of day it was sent and usethat inferred intent to select advertisements. Advertisements may have aset of related intent profiles associated with them. A system embodimentmay attempt to match the intent associated with the message and theintent associated with the advertisement to determine a match. Theadvertisement with a quality match may be selected and sent to thehandset or other similar device along with the voicemail message. If theuser selected that particular voicemail for display, the handset orother similar device may show them the selected advertisement beforedisplaying the content of the message. For example, a voicemail sentaround lunchtime may be associated with an advertisement for arestaurant.

3.7.1.4. Location

A system embodiment may infer a location from the content of themessage. The location itself or factors derived from the location may beused to select advertisements.

3.7.1.4.1. Embodiment: Infer Location from Voicemail Content

One possible embodiment of this system embodiment may extract locationinformation from the content of the message to select advertisements.For example, the voicemail may contain the phrase “meet in Palo Alto”,which a system embodiment may extract and identify as the city of PaloAlto, Calif. Advertisements may have a set of related locationsassociated with them. A system embodiment may attempt to match thelocations associated with the message and the locations associated withthe advertisement to determine a match. The advertisement with a qualitymatch may be selected and sent to the handset or similar device alongwith the voicemail message. If the user selected that particularvoicemail for display, the handset or other similar device may show themthe selected advertisement before displaying the content of the message,for example.

3.7.2. User-Specific Factors

One set of factors that may be used for selecting advertisements arefactors that are specific to the user or to their received message.

3.7.2.1. Calling Profile

A system embodiment may use the calling profile of a recipient of avoicemail message as a factor in the selection of an advertisement todisplay. The calling profile may be used to group related types of userstogether, or alternatively, to determine the demographic group(s) withwhich the user is associated. Such demographic groups may include one ormore of, but are not limited to: occupation, gender, region, and age.Any single factor of or combination thereof of the group membershipand/or demographic association(s) may be used to select advertisements.

3.7.2.1.1. Embodiment: Infer Demographic Group of Recipient Based onMobile Usage Pattern

One possible embodiment of this system embodiment may infer thedemographic group(s) of the recipient based on the calling profile ofthe recipient. For example, a recipient who calls frequently at nightmay have a higher likelihood of being a younger individual than someonewho call during the morning and early afternoon. If so, advertisementsmay have a set of related demographic group(s) associated with them. Asystem embodiment may attempt to match the demographic group(s)associated with the recipient and the demographic group(s) associatedwith the advertisement to determine a match. The advertisement with aquality match may be selected and sent to the handset or similar devicealong with the voicemail message. If the user selected that particularvoicemail for display, the handset or other similar device may show themthe selected advertisement before displaying the content of the message,for example.

3.7.2.2. Profile from Carrier Records

A system embodiment may use the user profile from the carrier of arecipient of a voicemail message as a factor in the selection of anadvertisement to display, assuming it is legally accessible. The datacontained in the user profile may be used to select the advertisement todisplay, or may be used to identify which demographic or related groupthe user belongs to, and that group membership may be used to select theadvertisement. Such demographic groups may include one or more of, butare not limited to: occupation, gender, region, and age. Any singlefactor of or combination thereof of the group membership and/ordemographic association(s) may be used to select advertisements.

3.7.2.2.1. Embodiment: Target Advertising Based on Recipient's CustomerRecord with Carrier

One possible embodiment of this system embodiment may infer thedemographic group(s) of the recipient based on the user record andprofile of the recipient stored on the carrier system embodiment. Forexample, the user record maintained by the carrier may store therecipient's age, from which a system embodiment may infer a demographicgroup. Advertisements may have a set of related demographic group(s)associated with them. A system embodiment may attempt to match thedemographic group(s) associated with the recipient and the demographicgroup(s) associated with the advertisement to determine a match. Theadvertisement with a quality match may be selected and sent to thehandset or other similar device along with the voicemail message. If theuser selected that particular voicemail for display, the handset orsimilar device first show them the selected advertisement beforedisplaying the content of the message, for example.

3.7.2.3. Historical Response

A system embodiment may use the historical responses of the recipient topreviously displayed advertisements as a factor in the selection of anadvertisement to display. This data may be used to create a profile ofpreferences for the recipient. The data in the profile may be used toselect the advertisement to display, or may be used to identify whichdemographic or related group the user belongs to, and that groupmembership may be used to select the advertisement. Such demographicgroups may include, but are not limited to, one or more of: occupation,gender, region, and age. Any single factor of or combination thereof ofthe preferences, group membership and/or demographic association(s) maybe used to select advertisements.

3.7.2.3.1. Embodiment: Target Advertising Based on Recipient's Responseto Earlier Ads

One possible embodiment of this system embodiment may store that aparticular advertisement was shown to a user and may record whether ornot that advertisement generated a response. This historical informationmay be used to select advertisements, or to infer the demographicgroup(s) of the recipient and use that inferred demographic group(s) toselect advertisements. For example, a system embodiment may infer that aparticular user is female based on the user's historical responses toadvertisements oriented towards females. Advertisements may have a setof related demographic group(s) associated with them. A systemembodiment may attempt to match the demographic group(s) associated withthe recipient and the demographic group(s) associated with theadvertisement to determine a match. Alternatively, advertisements may beselected on the basis of whether the user has historically responded toadvertisements of that type. If the user has historically not respondedto a specific advertisement or type of advertisement, that particularadvertisement or type of advertisement is not selected. If the user hashistorically responded, the advertisement is selected. A combination ofhistorical response and demographic group(s) may also be used; forexample, to narrow the range of advertisements that may be matchedagainst. The advertisement with a quality match may be selected and sentto the handset or similar device along with the voicemail message. Ifthe user selected that particular voicemail for display, the handset orsimilar device may show them the selected advertisement beforedisplaying the content of the message, for example.

3.7.3. Environmental Factors

A system embodiment may use factors that are not specific to the user,but instead are specific to their current environment, such as time ofday or location, to select advertisements.

3.7.3.1. Location

A system embodiment may use the current location of the user as a factorin the selection of an advertisement to display. The location itself orfactors derived from the location may be used to select advertisements.

3.7.3.1.1. Embodiment: Use Connected Cell Tower as a Proxy for Location

One possible embodiment of this system embodiment may use the cell towerto which the handset or other similar device was currently coupled as aproxy for the current location of the recipient. A system embodiment mayuse the derived location to select advertisements. Advertisements mayhave a set of related locations associated with them. A systemembodiment may attempt to match the locations associated with themessage and the locations associated with the advertisement to determinea match. The advertisement with a quality match may be selected and sentto the handset or other similar device along with the voicemail message.If the user selected that particular voicemail for display, the handsetor other device may show them the selected advertisement beforedisplaying the content of the message, for example.

3.7.3.1.2. Embodiment: Select Ads for Display Based upon or soon afterRecipient's Current Location

One possible embodiment of this system embodiment may use the currentlocation of the user from the handset or other similar device to selectadvertisements. Advertisements may have a set of related locationsassociated with them. A system embodiment may attempt to match thelocations associated with the message and the locations associated withthe advertisement to determine a match. The advertisement with a qualitymatch may be selected and sent to the handset or other similar devicealong with the voicemail message. If the user selected that particularvoicemail for display, the handset or similar device may show them theselected advertisement before displaying the content of the message, forexample.

3.7.3.2. Time of Day

A system embodiment may use the current time of day of the user as afactor(s) in the selection of an advertisement to display. The time ofday itself or factors derived from the time of day may be used to selectadvertisements.

3.7.3.2.1. Embodiment: Infer Intent of Voicemail Through Time of DayReceived

One possible embodiment of this system embodiment may infer the intentof the user on the basis on the current time of day and use thatinferred intent to select advertisements. For example, a systemembodiment may infer that the user may be hungry at 6 pm and may beinterested in receiving an advertisement related to dinner.Advertisements may have a set of related intent profiles associated withthem. A system embodiment may attempt to match the intent associatedwith the message and the intent associated with the advertisement todetermine a match. The advertisement with the best match may be selectedand sent to the handset or other similar device along with the voicemailmessage. If the user selected that particular voicemail for display, thehandset or other similar device may show them the selected advertisementbefore displaying the content of the message, for example.

3.7.4. Use of Multiple Factors in Targeting Advertisements

A system embodiment may more than one factor, and of various factortypes, to select advertisements.

3.7.4.1. Embodiment: Combining User-Specific with Environmental Factorsto Increase Ad Effectiveness

One possible embodiment of this system embodiment may combineuser-specific factors with environmental factors to selectadvertisements. Advertisements may have a set of related factorsassociated with them, and a weight for a factor. For example, a poolhall advertisement may weight the keywords “pool” and “bar” along withevening message times, messages between friends and a male demographic.A system embodiment may attempt to match the factors listed with theadvertisement and the factors from the user and environment. Matchingfactors may be weighted appropriately to generate a weighted matchscore. The advertisement with a quality match may be selected and sentto the handset or other similar device along with the voicemail message.If the user selected that particular voicemail for display, the handsetor other similar device may show them the selected advertisement beforedisplaying the content of the message.

3.7.5. Improvements in Factor Identification and Accuracy

A system embodiment may contain processes to improve the identificationand accuracy of the factors listed above.

3.7.5.1. Improve User Profile Demographics Through the Use of Surveys orOther Methods to Elicit Demographic Information

A system embodiment may provide for user profile demographics to be moreaccurately defined through the use of surveys. A system embodiment maysegment profiles based on collected data and other characteristics.However, this may identify what users are related and how, but withoutcharacteristics of their demographics. Surveys or other methods may beused to elicit demographic characteristics from a representative sampleof users from a user segment identified. Other users in that segment maybe inferred to have a similar demographic profile.

For example, a system embodiment may determine that two groups of usersexist: one group that frequently receives calls in the morning and onethat frequently receives calls at night. Further data may be providedvia a survey. For example, a survey of the users asking them their joboccupation may determine that the morning group are often businesspeoplewhile the evening group are often young individuals with an activenightlife.

3.7.5.2. Improve Automatic Message Profiling Through Manual MessageProfiling

A system embodiment may provide for message profiles to be moreaccurately defined through the use of manual and/or automaticidentification of message profiles. Incoming messages may be profiled bya system embodiment. Certain messages may be selected, by selectingthose where the automatic profiling reached a less certain or no result.Selected messages may be forwarded to manual profilers, who categorizethe message. The categorized message may sent back to the main systemembodiment. A system embodiment may use the manual data to train theautomatic profiler to better profile messages.

It will, of course, be understood that, although particular embodimentshave just been described, the claimed subject matter is not limited inscope to a particular embodiment or implementation. For example, oneembodiment may be in hardware, such as implemented to operate on adevice or combination of devices, for example, whereas anotherembodiment may be in software. Likewise, an embodiment may beimplemented in firmware, or as any combination of hardware, software,and/or firmware, for example. Likewise, although the claimed subjectmatter is not limited in scope in this respect, one embodiment maycomprise one or more articles, such as a storage medium or storagemedia. This storage media, such as, one or more CD-ROMs and/or disks,for example, may have stored thereon instructions, that when executed bya system, such as a computer system, computing platform, or othersystem, for example, may result in an embodiment of a method inaccordance with the claimed subject matter being executed, such as oneof the embodiments previously described, for example. As one potentialexample, a computing platform may include one or more processing unitsor processors, one or more input/output devices, such as a display, akeyboard and/or a mouse, and/or one or more memories, such as staticrandom access memory, dynamic random access memory, flash memory, and/ora hard drive.

In the preceding description, various aspects of the claimed subjectmatter have been described. For purposes of explanation, specificnumbers, systems and/or configurations were set forth to provide athorough understanding of the claimed subject matter. However, it shouldbe apparent to one skilled in the art having the benefit of thisdisclosure that the claimed subject matter may be practiced without thespecific details. In other instances, well-known features were omittedand/or simplified so as not to obscure the claimed subject matter. Whilecertain features have been illustrated and/or described herein, manymodifications, substitutions, changes and/or equivalents will now occurto those skilled in the art. It is, therefore, to be understood that theappended claims are intended to cover all such modifications and/orchanges as fall within the true spirit of the claimed subject matter.

1. A system for recording, transcribing and delivering voice messages,the system comprising: a server adapted to record a received voicemessage in a native audio format, convert the recorded audio format to atext representation of the message, convert the recorded audio format toan output audio format, and communicate the output audio format and textrepresentation to an output device.
 2. The system of claim 1, whereinthe native audio format comprises at least one of a WAV audio file, oran MP3 audio file.
 3. The system of claim 1, wherein the output devicecomprises at least one of a mobile phone or interface device.
 4. Thesystem of claim 1, wherein the output device comprises a mobile phonewith two clients; a message detection module implemented in code nativeto the mobile phone, and a message client implemented in code not nativeto the mobile phone.
 5. The system of claim 4, wherein code not nativeto the mobile phone comprises at least one of Java from SUNMicrosystems, Flash from Adobe Systems (“Flash”), HTML, or a combinationof Javascript and HTML (“AJAX”).
 6. A method for recording, transcribingand delivering voice messages, the method comprising: capturing areceived voice message in a native audio format; converting the nativeaudio format to a text representation of the message; converting thenative audio format to a output audio format; and communicating the textrepresentation and output audio format of the message to an outputdevice.
 7. The system of claim 1, wherein the output device is operableto store the output audio format of all received voice messages.
 8. Thesystem of claim 1, wherein the output device is operable to store theoutput audio format of a subset of received voice messages and isoperable to retrieve the output audio format for non-stored messagesand/or the messages on demand through a data connection with the server.9. The system of claim 1, wherein the output device is operable toretrieve the output audio format and/or messages in the format on demandfrom the server as requested by a control module of the output device.10. The system of claim 9, wherein the output device is operable toretrieve the output audio format and/or messages in the format via adata connection.
 11. The system of claim 10, wherein the data connectioncomprises a cellular network.
 12. The system of claim 10, wherein thedata connection comprises a wireless fidelity (“Wi-Fi”) network.
 13. Thesystem of claim 10, wherein the data connection comprises an IP network.14. The system of claim 9, wherein the data connection is capable ofproviding access to voicemail messages.
 15. The system of claim 14,wherein the output device is operable so that a particular message forwhich the audio is to be accessed is identified through a combination ofthe caller's telephone number and the call-in telephone number on thesystem.
 16. An apparatus comprising: a voice message delivery system,said system including a server adapted to select an advertisement for avoice message, and a client adapted to receive and display the selectedadvertisement in conjunction with the voice message.
 17. The system ofclaim 16, wherein the selection mechanism for advertisements is operableto employ one or more targeting factors.
 18. The system of claim 17,wherein the selection mechanism for advertisements is operable to employthe text representation of the voice message as one or more targetingfactors.
 19. The system of claim 18, wherein the targeting factors arederived at least in part from attributes of the message.
 20. The systemof claim 18, wherein the targeting factors are derived at least in partfrom attributes of the sender.
 21. The system of claim 18, wherein thetargeting factors are derived at least in part from attributes of therecipient.
 22. The system of claim 18, wherein the targeting factors arederived at least in part from attributes of the recipient's currentenvironment, including time of day or location.
 23. The system of claim18, wherein the targeting factors are derived at least in part from acombination of one or more of attributes of the message includingrecipient, sender, or current environment.
 24. The system of claim 19,wherein the targeting factors are derived at least in part from the texttranscription of the message.
 25. The system of claim 19, wherein thetargeting factors are derived at least in part from application of aprofile to the text transcription of the message.
 26. The system ofclaim 20, wherein the targeting factors are derived at least in partfrom the identity of the sender.
 27. The system of claim 20, wherein thetargeting factors are derived at least in part from inferred preferencesof the sender.
 28. The system of claim 20, wherein the targeting factorsare derived at least in part from an inferred relationship between thesender and recipient.
 29. The system of claim 28, wherein the inferredrelationship between sender and recipient is derived at least in partfrom the attributes of the sender's entry in the address book of therecipient.